NetApp
Storage Virtual Machine : Protection : SnapMirror : Managing mirror relationships for Data ONTAP 8.2 : Breaking SnapMirror relationships
Breaking SnapMirror relationships
You must break the mirror relationship if a mirror source becomes unavailable and you want client applications to be able to access the data from the mirror destination. After the mirror relationship is broken, the destination volume type changes from DP to RW.
Before you begin 
•
The SnapMirror destination must be in the quiesced or idle state.
•
The destination volume is premounted into the destination Storage Virtual Machine (SVM) namespace
About this task 
You can use the destination volume to serve data while you repair or replace the source, update the source, and reestablish the original configuration of the systems.
Steps 
1.
From the home page, double-click the appropriate storage system.
2.
Expand the Storage Virtual Machines hierarchy in the left navigation pane.
3.
Select the SVM that contains the destination volume and click Protection.
4.
Select the mirror relationship that you want to break.
5.
Click Operations > Break.
6.
Select the confirmation check box and click Break.
Result 
The data protection SnapMirror relationship is broken. The destination volume type changes from data protection (DP) read-only to read/write. The system stores the base Snapshot copy for the data protection mirror relationship for later use.
For Infinite Volumes, a namespace mirror constituent is required on the destination volume to provide data protection to the namespace constituent. Therefore, a new mirror is created on the Infinite Volume, if the namespace mirror constituent does not already exist.
Related reference 
Protection window

Was this topic helpful? Send comments to NetApp.